Raw Lendlord API request

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real value beyond the annotations: encryption is handled automatically, GET is read-only while other methods mutate data, and non-GET calls require write confirmation. This usefully refines the coarse destructiveHint=true into a per-method rule. It does not cover rate limits, error shapes, or how raw responses are returned, keeping it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler. The capability, the fallback trigger, and the safety rule are all front-loaded in that order, which matches how an agent decides whether to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-world passthrough with no output schema and 40% parameter coverage, the description supplies the essentials: what it reaches, that encryption is automatic, and that writes need confirmation. The remaining gap is that it outsources the endpoint list to docs/api.md and says nothing about failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% across five parameters. The description clarifies method semantics (GET vs. others) and ties into the confirm parameter via 'write confirmation', but it never explains the required /api/ path pattern, the query map, or the body format beyond 'encryption handled'. Partial compensation for a genuine coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Call any Lendlord /api endpoint directly') and frames itself as the fallback for features lacking a dedicated tool, which distinguishes it from the long list of purpose-built siblings. An agent can immediately tell this is the escape hatch rather than a domain operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear condition for use ('features without a dedicated tool') and points to docs/api.md for the endpoint catalogue. It stops short of naming which siblings to prefer first, and defers endpoint discovery to an external file, so it is clear context but not fully self-contained routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.