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

readOnlyHint already declares the safety profile, so 'Read-only' adds little, but the description does add two things annotations cannot: an authentication prerequisite ('Needs a TenderCrest account') and an ownership constraint (only the signed-in user's own proposals are readable). It stops short of describing response size, pagination, or what happens if the ID belongs to another user.

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?

Two sentences, front-loaded with verb and scope, then the returned content list, then the two constraints. Nothing is repeated or redundant, and the enumeration substitutes for the absent output schema rather than padding.

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?

With no output schema, the description correctly compensates by listing what the read returns, and it covers the auth prerequisite and ownership scope. What's missing for a full-record read is volume/pagination expectations and error behavior for inaccessible IDs — minor but relevant for an agent planning a large fetch.

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?

There is a single required parameter whose schema description is already complete and even names its source tool ('Proposal ID from list_proposals'). The prose adds no format, sourcing, or failure semantics for projectId, so the schema carries the load entirely.

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 ('Read ... proposals in full'), scopes it to 'the signed-in user's own' proposals, and enumerates the payload (sections, requirements, evidence decisions, jobs, files, activity, approvals, readiness). That enumeration implicitly separates it from the list-level sibling and from a single-revision getter, so an agent can tell what it returns without opening the schema.

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?

Usage is only implied: 'one of the signed-in user's own proposals' and 'in full' suggest it follows ID discovery, and the parameter points at list_proposals, but the description never states when to prefer this over a list or revision-level read. The only explicit precondition given is the account requirement.

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