SitecoreMCP

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

No annotations are provided, so the description carries the full burden. It describes the tool's function (introspection) and timing (before queries), but doesn't disclose behavioral traits like whether it's read-only, has side effects, rate limits, or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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?

The description is perfectly concise and front-loaded: a single sentence that immediately states what the tool does and when to use it. Every word earns its place with no redundancy or unnecessary elaboration. The structure flows logically from function to usage context.

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?

Given the tool's complexity (introspection operation with no parameters) and the absence of both annotations and output schema, the description is minimally complete. It explains what the tool does and when to use it, but doesn't describe what the schema information looks like, how it's returned, or any limitations. For a schema introspection tool, more detail about the output format would be helpful despite the lack of output schema.

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?

The tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters since none exist. However, it could have mentioned that no parameters are required, which would be helpful context. The baseline for 0 parameters is 4, as the description adequately addresses the parameter-free nature through its functional explanation.

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?

The description clearly states the tool's purpose: 'Introspection Sitecore GraphQL master schema' and 'use this tool before doing a query to get the schema information'. It specifies the verb ('introspection'), resource ('Sitecore GraphQL master schema'), and context ('before doing a query'). However, it doesn't explicitly differentiate from its sibling 'introspection-graphql-web', though the 'master' vs 'web' distinction is implied.

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?

The description provides clear usage context: 'use this tool before doing a query to get the schema information if you do not have it available as a resource already'. This gives explicit guidance on when to use it (before queries when schema info is unavailable). However, it doesn't mention when NOT to use it or explicitly compare with the 'introspection-graphql-web' sibling tool.

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